Skip to content

[9.0](backport #9865) Add ingest-docs team as CODEOWNERS for release notes and docset.yml #9980

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Sep 17, 2025
Merged

[9.0](backport #9865) Add ingest-docs team as CODEOWNERS for release notes and docset.yml #9980

merged 2 commits into from
Sep 17, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Sep 16, 2025

Related to #9440

Adds ingest-docs team as CODEOWNERS for docs/release-notes and docset.yml.

In my experience, someone with admin rights in this repo will need to add the @elastic/ingest-docs team with write permissions even if all of elastic already has write access.

When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.

From: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

This is an automatic backport of pull request #9865 done by Mergify.

@colleenmcginnis @mergify
add ingest-docs team as CODEOWNERS for release notes and docset.yml (#…
599b06c 
…9865)

(cherry picked from commit c8f5f63)

# Conflicts:
#	.github/CODEOWNERS
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Sep 16, 2025
@mergify mergify bot requested a review from a team as a code owner September 16, 2025 02:25
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Sep 16, 2025
@mergify mergify bot added the backport label Sep 16, 2025
@mergify Mergify
Copy link
Contributor Author

mergify bot commented Sep 16, 2025

Cherry-pick of c8f5f63 has failed:

On branch mergify/bp/9.0/pr-9865
Your branch is up to date with 'origin/9.0'.

You are currently cherry-picking commit c8f5f631f.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/CODEOWNERS

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@github-actions github-actions bot added documentation Improvements or additions to documentation docs skip-changelog labels Sep 16, 2025
@colleenmcginnis
Copy link
Contributor

Backporting to 9.0 so the ingest-docs will be tagged to review PRs like #9926.

@colleenmcginnis colleenmcginnis merged commit cfd5930 into 9.0 Sep 17, 2025
12 checks passed
@colleenmcginnis colleenmcginnis deleted the mergify/bp/9.0/pr-9865 branch September 17, 2025 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pierrehilbert pierrehilbert pierrehilbert approved these changes

Assignees

@colleenmcginnis colleenmcginnis

Labels

backport conflicts There is a conflict in the backported pull request docs documentation Improvements or additions to documentation skip-changelog

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@colleenmcginnis @pierrehilbert